I have a bit of problem here and it has been driving me mad for a few days.... I am using SharePoint 2007 sp1 on Windows 2003 sp3. I have one APP server and 2 WFE servers. The installation was good with no major issues. However, when I tried to install a 3-rd SharePoint workflow and reporting product it ran ok with the installations but then any link I tried to click on get the "Could not load the assembly" problem. I checked the 12-hives log and Windows IIS log but it does not seem to report any errors. According to my instructions, the product is installed on the APP server and I would see the DLLs applied to the GAC on the WFE servers. The token and signatures match with the ASPX page that requests the assembly.... I am wondering what is the best approach to track this problem? (I have already turned the trace on but does not seem to get anywhere for me) Thanks for any help in advance. W

Just a passing thought: Are all your servers in the farm at the same Patch level (service packs, versions, etc)? If you uninstall your 3-rd party Workflow are you able to use your SharePoint site properly?BR, PM

Hi, besdie prasanjit provided, can you change security level to full and make sure that impersonation property is true in web.config?Best Regrads, Ahmed Madany

The Patch level should be the same for all servers...if I uninstall the 3-rd party product the site will not behave 100%...anyway I have attached the error here.... (for the 3rd party reporting tool) Could not load the assembly 'xxx.xxxx.xxxx.xxxx, Version=1.0.0.0, Culture=neutral, PublicKeyToken=df8bc1a8465564d9'. Make sure that it is compiled before accessing the page. at System.Web.UI.TemplateParser.GetType(String typeName, Boolean ignoreCase, Boolean throwOnError) at System.Web.UI.TemplateParser.ProcessInheritsAttribute(String baseTypeName, String codeFileBaseTypeName, String src, Assembly assembly) at System.Web.UI.TemplateParser.PostProcessMainDirectiveAttributes(IDictionary parseData) (for the 3rd party workflow tool) File Not Found. at System.Reflection.Assembly._nLoad(AssemblyName fileName, String codeBase, Evidence assemblySecurity, Assembly locationHint, StackCrawlMark& stackMark, Boolean throwOnFileNotFound, Boolean forIntrospection) at System.Reflection.Assembly.nLoad(AssemblyName fileName, String codeBase, Evidence assemblySecurity, Assembly locationHint, StackCrawlMark& stackMark, Boolean throwOnFileNotFound, Boolean forIntrospection) at System.Reflection.Assembly.InternalLoad(AssemblyName assemblyRef, Evidence assemblySecurity, StackCrawlMark& stackMark, Boolean forIntrospection) at System.Reflection.Assembly.InternalLoad(String assemblyString, Evidence assemblySecurity, StackCrawlMark& stackMark, Boolean forIntrospection) at System.Reflection.Assembly.Load(String assemblyString) at System.Web.Configuration.CompilationSection.LoadAssemblyHelper(String assemblyName, Boolean starDirective) To me it does sound like security issue but I am a bit of a SharePoint newbie and not sure how to tackle the problem.... Thanks

Anyway it turns out to the a problem of the 3-rd party product and the company that wrote the software has provided a solution for me...thanks everyone

What is the solution? Thanks!

We are using Nintex Workflow and the company send us a patch (11004N) which have fixed the problem.